Partitioned Server - The TCP/IP stack can't bind a network address to a TCP socket

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject: Partitioned Server - The TCP/IP stack can't bind a network address to a TCP socket

Feedback Type: Problem

Product Area: Domino Server

Technical Area: Error Message

Platform: Windows

Release: 8.5.2

Reproducible: Always

I seem to be having trouble setting up a partition on my Domino server. My Windows 2008 server has 3 separate IP addresses set up on a single network card. I've got 2 partitions working successfully on 2 of the IP addresses but I just can't seem to get the third one going.

I've set it up in exactly the same way as the other partitions, modifying the notes.ini to use the correct IP address in the TCPIP_TCPIPAddress parameter, and the server starts without any errors appearing, but whenever I try to connect to the new partition using a client I'm getting the error "The TCP/IP stack can't bind a network address to a TCP socket, please verify that the TCP stack has been properly intialized"

I can telnet various ports on that ip address from the server itself, but not from outside the server. I can use Domino trace to trace the server from itself, but not from another server. I can use a browser to make an http connection to the server from the server itself, but not from another machine. I also can't get this new Domino server to connect to an existing server in the same Domino domain - it's getting the correct IP address from a connection document and there's definitely a connection available but the new server is telling me that the original server is down.

I've been googling this all day but the only solution I can find to this error is making sure the correct IP address is in the TCPIP_TCPIPAddress parameter, which it is for all 3 servers.

I've got a feeling that this could be a windows/networking issue rather than a Domino issue because I get that error message even if the server is not running (I would expect to get 'The server is not responding' or 'The remote server is not a known tcpip host'), and connectivity seems to be OK from the server itself, but I don't know enough either way to make a judgement.

Is it possible that this third IP address isn't "working" as an external IP address? Is this likely to be a Windows Firewall thing? I can't see anything in there which would block this one IP address and not the two others.

If anyone's got any suggestions, I'd be really grateful because I'm at the stage where I just feel like I'm banging my head against a brick wall now!
Thanks,
Emily.

Feedback number WEBB8F8M2D created by ~Mario Rejipyzenader on 03/23/2011

Status: Open
Comments: